-
Notifications
You must be signed in to change notification settings - Fork 149
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
refactor: remove references of broadcastRawTransaction, use only broadcastTransaction #4900
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice work @edgarkhanzadian, really great getting a new set of eyes on this code and seeing improvements. 👍
This is great refactor, but a little concerned this changes behaviours of sponsors transactions, this logic isn't in the other broadcast fn right? |
Good point, thinking that can just be relocated? |
@fbwoolf @kyranjamie i tried replicating the sponsored functionality at 3e7af19 but i am not 100% sure that it works, how can i test it? |
I believe there is a sponsored tx in the test-app to use? |
Alex swap uses sponsored txs right @fbwoolf ? Can't we use that to test? |
@kyranjamie i tried with a test app and it seems to be working for me, we can also try alex swaps |
Also, noticed an infinite loop on fee UI. Sponsored transactions shouldn't have any fees, but there is currently an infinite loop caused by the useEffects. Fixed infiniteLoop.mov |
Merging. Please, don't include it in this release yet: #4918 |
c3a0354
to
0527317
Compare
cc5985d
to
2a6b0a0
Compare
2a88579
to
f5ec86c
Compare
Instead of using broadcastRawTransaction in one place and broadcastTransaction in another, it would be better to use only one function everywhere for consistency. Here's my take on refactoring that part.
Testing with the broadcastTransaction:
signingContract.mov